Release notes for version 3.25.0
This article contains the release notes for Neuron Power Engineer version 3.25.0.
Up-to-date information within online-version Please check the online-version (provided under https://help.neuron-automation.eu) whether new pieces of information have been added since this user manual (as PDF/HTML/Word) has been published; e.g. the release notes quote new problems or there are new articles in the troubleshooting- or FAQ-section. |
Release-Notes for previous versions of Neuron Power Engineer are provided in the online-version under https://help.neuron-automation.eu only.
In this article: |
---|
General information
About compatibility: |
If you have used a previous version of Neuron Power Engineer and you want to use the current version, see "Are my projects upwards and downwards compatible?" for important information. Recommended, if you are using projects that have been created in a previous version of Neuron Power Engineer: Clean the imported projects.
|
|
On the Log4j security vulnerability: |
See "Is the IDE affected by the Log4j security vulnerability (December 2021, CVE-2021-44228, Log4Shell)". |
|
About system libraries: |
||
About the illustrations in the IDE documentation: |
Depending on the configuration of your Neuron Power Engineer version, the FBD-editor and its elements might be displayed differently in your Neuron Power Engineer version than illustrated in the IDE documentation. This is the case, if Neuron or the system integrator has activated the smart styling or one of them has changed the styles for the FBD-editor. Subsequently, the illustration in the IDE documentation are symbolic images and the representation in your Neuron Power Engineer version takes precedence for the valid representation. In case of doubts, please contact Neuron or your system integrator. See "Color and style for FBD-elements determined by data type" for details. |
General information for runtime system and target systems
About the →runtime system : |
If you are using Neuron Power Engineer version 3.25.0, install and use the version 5.20.0 of the runtime system.
|
About →Raspberry Pi : |
See the tutorial "Putting Raspberry Pi into operation" which version is recommended by Neuron for usage. |
About the runtime system for safety projects: |
If you are using logi.µSRTS version V1.0.0 (with a logi.µSRTS Core version ≥ 1.17.0) or V2.0.1 (with a logi.µsRTS Core version V2.0.0) together with the current version of Neuron Power Engineer, observe that the alarm messages of these logi.µSRTS versions are still containing the previous product name of the development environment. This previous product name is "logi.CAD 3" whereas the current product name is "Neuron Power Engineer". In spite of the previous product name, the alarm messages apply to Neuron Power Engineer as well. |
New features in Neuron Power Engineer version 3.25.0
This section informs you about the latest new features for this version.
ID |
Component |
New feature |
---|---|---|
59872 | PLCopen blocks |
The library
These blocks are based on the technical specification "TC5 - Safety, Version 2.10 – Official Release, Part 1 - Concepts and Function blocks" (© PLCopen TC5 - Safety, Version 2.01 – Official Release, Part 1 - Concepts and Function blocks" (© PLCopen) whereas the description in the IDE documentation is still based on the version 2.01 of the technical specification like all descriptions for the PLCopen blocks are still based on the version 2.01 of the technical specification. As soon as the descriptions are updated to version 2.10, the topic “PLCopen blocks” will state so. Observe that the library |
111279 | Safety parameter editor | Now the representation of floating point values in the safety parameter editor always uses "." as a decimal separator. In previous versions, the decimal separator depended on the regional settings of the operating system and the selected language of the IDE. |
111704 | Safety parameter editor |
The safety parameter editor provides the default commands and shortcuts for saving. For instance, you are able to use the command Save in the menu File or the keyboard shortcut Ctrl+S. See “Saving safety parameter editor” for more details on the current saving methods. |
111738 | Safety parameter editor | Now it is possible to resize a column in the safety parameter editor. See “Components of the safety parameter editor“, if you need details on this resizing. |
112140, part 1 | Global-variables-editor |
The provided actions within the global-variables-editor have been revised as follows:
|
112140, part 2 | Global-variables-editor |
Neuron Power Engineer allows to differ between 2 types of global objects containing global variables:
These 2 types of global objects make it possible to provide 2 different configuration sets that influence the global-variables-editor as follows:
Notes:
|
112223, part 1 | Vendor blocks |
When creating and saving the interface of the vendor blocks (provided in an ST-object), a header file (= H-file) and an optional C file with so-called implementation stubs are automatically generated. In previous versions, a 2nd, 3rd, 4th etc. saving action did not update these implementation stubs. In this case, the recommended procedure was to rename the automatically generated files to a unique name, to save the ST-object again to make sure that the generated files contained the correct implementation stubs and to transfer your code to the newly generated C-/H-files and delete the renamed C-/H-files. These steps had to be done for each saving action. To provide more user comfort, apply this procedure for your vendor blocks once in the new version:
The parts outside the auto-generated implementation stubs will not be touched so that your code in the H-/C-file will not be overwritten when saving the ST-object containing your vendor block again. Observe that the auto-generated implementation stubs for some types of vendor blocks are not decorated with the preceding comment |
112223, part 2 | Perspectives | The main toolbar directly beneath the menu bar provides 2 new buttons to open these perspectives: Application Testing and Application Creating (Application Navigator) |
112223, part 3 | ST-editor, Inserting variables | It is possible to drag and drop a variable from the Instances view into an ST-editor, in particular the body of a POU. The name of the variable is inserted in the code when this variable exists in the POU. See “Entering ST-code” for details on dragging and dropping variables. |
112226 | Safety parameter editor |
You can call a help page for a parameter if the system integrator has provided such a help page: Just select the parameter in the safety parameter editor and press the F1-key. See “Opening help for parameters from witin the safety parameter editor“. |
112696 | PACK block, vendor blocks |
The In previous versions, the return value of As a consequence, the The statement |
112981 | Validating an application |
The standard package of the IDE provides the new rule Only actual resource-global variables must be used in the VAR_CONFIG sections. This model rule checks whether the By default, this rule is not activated so you will not get any messages about violations of this rule when the application is validated. But as for other rules, you can change the configuration of the rule. |
113354 | Safety-relevant applications, IDE documentation | The IDE documentation contained the section “Safety instructions on working with the IDE”. This section has been removed from the IDE documentation, because this documentation is provided by a system integrator to the end users who want to develop safety-relevant applications and libraries in compliance with the relevant safety standards. If you are interested in the documentation provided in this section, please get in touch with your system integrator to clarify how you can obtain this documentation in future. |
113408 | Standard library, system blocks |
The existing system library
Observe:
|
113549 | Validating an application |
The standard package of the IDE provides the new rule Multiple writing of hardware outputs within a resource is not permitted. This model rule checks whether hardware outputs are written in more than one program instance of a resource. Global variables with an assigned IEC hardware address are regarded as hardware outputs. Writing such variables is only permitted in exactly one program instance of a resource. By default, this rule is not activated so you will not get any messages about violations of this rule when the application is validated. But as for other rules, you can change the configuration of the rule. |
114002 | IDE, IDE documentation |
The IDE provides a new possibility to hide features and GUI (Graphical User Interface) elements. This deactivation is done by activating a profile. As the profile is activated by a system integrator, contact your system integrator on the current possibilities. Observe that the IDE documentation contains the descriptions for all officially provided features and GUI elements - no matter whether a profile has been activated or not. So, the scope of the IDE documentation is not updated to reflect the change in the IDE itself. |
113829 | IDE documentation |
The location of the IDE user documentation has been changed from: Mind the changed notation from “EN” to “en”. This change has been necessary for internal purposes. If you are using an outdated URL, you will be directed to: https://help.neuron-automation.eu/Documents/NPE/latest/en/Content/Redirection/RedirectInfo.htm - This topic informs you about possible steps after the redirection. |
New features relating to the runtime system and target systems
ID |
Component |
New feature |
---|---|---|
|
|
none |
Fixed problems in Neuron Power Engineer version 3.25.0
If not otherwise stated, this sections informs you about problems that have occurred in version 3.24.0 and have been fixed for the current version 3.25.0.
ID |
Component |
Fixed problem |
---|---|---|
59779 | FBD-editor, memory consumption | A memory leak occurs when scrolling through extensive FBD-objects.
Fix: The problem according to the following scenario does not occur anymore. Scenario for problem: If an FBD-editor with many pages/objects is opened for a longer period of time and the view onto to the contained pages/objects is changed (= you are scrolling through the FBD-editor), the memory consumption might increase considerably. As a result, it is no longer possible to operate the FBD-editor. Additional information: The display of the FBD-elements occupies memory. This memory is not freed if these FBD-elements are no longer displayed. The more FBD-elements are displayed by scrolling, the more memory is used. The problem might occur even earlier, if the FBD-editor contains many OLT-fields and data is displayed in these OLT-fields while testing/debugging. |
107379 | FBD-editor |
The IDE documentation differs from the implementation in a special case for replacing a block call.
Here is the illustration from the IDE documentation in which the value field with the access
However, this value field will not be highlighted as faulty. |
109235 | Safety-relevant applications |
The integration acceptance tests cannot be executed because of missing files.
|
109261 | Test framework, Gateway |
PiL-tests for more than 240 test suites are failing because of an unexpected termination of the Gateway.
|
109267 | Building the application, safety-relevant application |
When building a safety-relevant application, an error about a wrong checksum for the source file |
109982 | Safety-relevant applications |
The build report might contain error messages about unverified data types.
The source file "project_path/src-gen/h/lcdt___data_type_name.h" with checksum "checksum_value" could not be verified. |
110582 | Text files |
A message is displayed when entering “” at the beginning of a text file.
|
111534 | Building the application |
The application cannot be built when a function block instance is assigned/connected to the input of a The application for the PLC (resource "name1", platform toolkit "name2") cannot be created/loaded. Check the views "Error Log" and "Problems" for more information. After the attempt to build the application, messages are displayed in the Problems view. Here are the messages for the described scenario:
Additional information 1: The same problem also applies to other blocks, e.g. |
112265 |
PLCopen blocks |
Deviation in the technical specification for PLCopen blocks, current version 2.10 to previous version 2.01.
Fix: The problem according to the following scenario does not occur anymore. Scenario for problem: The implementations of the blocks EmergencyStop , ESPE and PSE were identical in the technical specification "TC5 - Safety, Version 2.01 – Official Release, Part 1 - Concepts and Function blocks" (© PLCopen). Since version 2.10 of this technical specification, the implementation of EmergencyStop does not follow the others blocks anymore.Neuron assumes that this is wrong in the technical specification and is currently clarifying this with PLCopen. Workaround: none existing |
112370 | Application navigator | The Application folder might not display any additional decorators, such as the decorator for errors/warnings.
Fix: The problem according to the following scenario does not occur anymore. Scenario for problem: Additional decorators within an object icon inform about the state of the object (e.g. that it is faulty or that there is a warning for this object). These decorators are also provided within a folder icon to inform about the states of the objects that are included in the folder. However, these decorators are missing for the Application folder. |
112386 | Application navigator | Renaming a configuration or resource in the application navigator does not update the associated items there.
Fix: The problem according to the following scenario does not occur anymore. Scenario for problem: When you rename a configuration or resource in the application navigator (e.g. by using the command Rename), the folders Sources for configuration and Sources for resources are not updated appropriately. Instead, these folders do not contain any objects anymore. This is because the associated folders for the configuration/resource have not been renamed as well. The project structure still displays the folders with the previous names whereas the Sources for configuration and Sources for resources folders are already looking for the objects in the folders with the new names. |
112523 | VarCfg-object, hardware addresses, building the application | The IO code is not synchronized/updated after some changes in the VAR_CONFIG hardware addresses.
Fix: The problem according to the following scenario does not occur anymore. Scenario for problem: When you change hardware addresses in the section VAR_CONFIG … END_VAR (inside a section RES_VARCFG … END_RES_VARCFG ), save the changes and you rebuild the application, the IO code is not updated as expected. Instead, the original hardware address is still being considered.Additional information: The file IOAccess.c is not generated anew. |
112715 | FBD-editor |
When using a different screen scaling that 100%, the FBD-editor might not behave as expected.
Additional information: The changed scaling seems to cause this problem. For both issues, the context text appears to be opened for a wrong FBD-element whereas the context menu is opened at the position of the current mouse cursor. Regarding example 1, the command to create the OLT-field appears to be disabled because the drawing field is incorrectly considered to be the valid context. |
112819 | Interface editor | The interface editor does not behave as expected when using smart styling and moving around in-/outputs.
Fix: The problem according to the following scenario does not occur anymore. But mind the restriction for smart styling that inputs can only be dragged to the left block edge while outputs can only be dragged to the right block edge. Scenario for problem: When you are using the smart styling for the FBD-editor, the interface editor uses this smart styling as well. When you drag inputs or outputs around to a new, empty position in the interface editor, The interface editor does not behave as expected. Additional information: The dragging of the inputs or outputs is done in the preview of the interface editor. |
112859 | Building the application | The process of building applications (initiated for a configuration) deletes the respective folders for each resource. This behavior is not as expected.
Fix: Now, the behavior according to the following scenario is as expected. Scenario for problem: While building the application for all resources of a configuration, the folders src-gen and target are deleted separately for each resource. However, the expected behavior is that both folders are deleted only once before the building process starts for the configuration. |
112882 | ST-editor | A piece of information on the declaration of VAR_INPUTs is incomplete.
Fix: The IDE documentation has been updated correspondingly. Scenario for problem: The IDE documentation on the declaration of input variables in ST contains this piece of information: Within a section VAR_INPUT...END_VAR, it is also possible to declare function block instances and to declare variables based on an interface. However, this is not true for functions. |
113101 | Application navigator, artifact identify, PLC object | Deleting a global-object might cause an invalid artifact identity of a PLC-object in which the global-object is used.
Fix: The problem according to the following scenario does not occur anymore. Scenario for problem: When you delete a global-object in the application navigator and this global-object is used in a PLC-object, the PLC-object is updated correctly. However, the artifact identity for the PLC-object is not updated as expected. This causes an error reporting the invalid artifact identity for the PLC-object. Additional information: The PLC-object contains an INCLUDE_GLOBALS directive referring to a GLOBALS section from the deleted global-object. This directive is removed from the PLC-object. |
113365 | ST-editor |
The IDE documentation on the
Scenario for problem 1: The IDE documentation contains information on declaring a language element with a partial address in ST. There the optional attribute OFFSET is described as well. The documentation is as follows:
Due to this information, it is unclear whether the offset is applied to the structure element or the variable that is based on the structured data type. Fix for problem scenario 2: The sample in the IDE documentation has been corrected so that the comment specifies the offset 61. Scenario for problem 2: The IDE documentation also contains samples that illustrate the impact of |
113751 | Safety-relevant applications, building the application |
Confusing messages are displayed that source files cannot be verified when the safety-relevant application is built for the built-in PLC.
Additional information:
|
113948 | IDE |
When aborting the exit procedure for the IDE, features in the opened IDE are not working as expected.
|
113981 | Safety parameter editor, IDE documentation |
The IDE documentation on the safety parameter editor (version 3.24.0) does not contain information on floating-point numbers.
The actual information should be (see the bold text that highlighted the missing detail):
|
114057 | Instances view |
The "Instances" view might not be updated correctly: Not all of the changed program instances are displayed.
Now the Instances view displays only one of the changed program instances although 3 instances have been changed. |
Changes affecting the code generation
The following changes in Neuron Power Engineer version 3.25.0 affect the automatically generated C-code (and thus the built application), even if you do not make any changes in the application yourself. Observe that when you load the application, the changed code will be loaded onto the PLC.
Change |
Starting with version |
More information on the change |
---|---|---|
none |
|
|
Note: The flag SAFETY means that the change must be taken into account in particular when developing safety-relevant applications. A change without this flag applies to a functionality/configuration which is not supported for the development of safety-relevant applications. |
Known problems in Neuron Power Engineer version 3.25.0
ID |
Component |
Known problem |
||
---|---|---|---|---|
49494 |
Application navigator, |
When several function blocks have been created in the same ST object, the command "Delete" in the application navigator deletes all function blocks in this ST object without any previous information.
|
||
49498 |
Application navigator |
The command "Go Into" in the application navigator does not behave as expected.
|
||
59175 |
Teaming up to create applications, vendor blocks |
The automatically generated H-/C-files for vendor blocks are not automatically locked. The editor for them is not opened in a read-only mode.
|
||
60703 |
Validating the application |
Syntax errors might be caused when using the content assist to suppress warnings for rule violations.
Workaround: none existing |
||
60726 |
IDE |
The changed file association is ignored for opening a data type from a library configuration.
|
||
60776 |
LD-editor |
No emphasis is displayed when reconnecting existing link elements within the LD-editor.
|
||
61171 |
Teaming up to create applications |
The "Team Monitor" view does not determine the status changes on the team server at the expected interval.
|
||
61175 |
Access control |
It is possible to turn a folder into a namespace folder and vice versa without the appropriate access control rights to edit the application logic.
Workaround: none existing |
||
61183 |
Access control |
It is possible to assign a USING instruction for accessing a namespace folder and delete this instruction without the appropriate access control rights to edit the application logic.
Workaround: none existing |
||
61187 |
Artifact identity |
The artifact identity is not created/updated when turning a folder into a namespace folder or assigning a USING instruction for accessing a namespace folder.
|
||
107348 |
Building the application |
Building an application might lead to linker warnings.
|
||
107419 |
Application navigator, namespaces |
Objects in nested namespace folders do not have a nested namespace.
|
||
107558 |
FBD-editor |
The initialization of structure elements is not possible when creating a new structured variable via the content assist.
|
||
107713 |
Access control |
An exception might be caused when importing an existing access rights configuration.
|
||
107764 | FBD-editor, Cleaning the project | FBD-elements are highlighted as faulty in the opened FBD-editor, if the corresponding C-file has been opened while cleaning the project.
Scenario for problem: If you have opened an FBD-editor and the corresponding C-file while the project is being cleaned, the lines and the connected block calls are highlighted as faulty in the opened FBD-editor. If you move the mouse pointer onto the error icon of the call, these messages are displayed for each block and block input: Could not resolve reference to '_name_'. A variable with this name does not exist. Additional information: Usually, C files are not displayed in the views with the resources (e.g. the project explorer). However, C files can be displayed in the project explorer, if you deactivate the src-gen folder filter for the view. In this case, it is also easy to open the editor for a C file from within the project explorer.Workaround: Close and reopen the FBD-editor |
||
107789 | Global-variables-editor | The sort order might not be as expected, when moving multiple global variables or sections in the global-variables-editor.
Scenario for problem: When you are moving multiple global variables or sections in the global-variables-editor, the variables or section might not be sorted as expected. Workaround: none existing |
||
108722 | PLCs, Connecting to the PLC |
After a failed loading of the application, GUI elements in the “Instances“ view might not be in sync.
Workaround: Click the button Connect to PLC again to update the state. Subsequently, the line Connection state displays Online with the execution state Error. |
||
112411 | FBD-editor, namespace | Error message about invalid namespace is not sufficiently visible in the FBD-editor.
Scenario for problem: If you enter an invalid namespace (e.g. 11 ) in the tab “Namespace” of the FBD-editor, an appropriate error message is displayed but the message is not entirely visible.Additional information: A namespace must be an IEC-identifier. See “→IEC-identifier” for details. Workaround: Enter an IEC-identifier as namespace to avoid getting the error message. |
||
112437 | Application navigator | An empty folder is displayed under the project, when a new folder is created under the “Application” folder.
Scenario for problem: When you create a new folder under the Application folder in the application navigator, an item without any name is displayed under the project folder. This empty item is automatically selected. Workaround: Refresh the view so that the empty item disappears. Do not delete this empty item. If you do anyway, the new folder will be deleted as well. In this case, just press Ctrl+Z to undo the deleting. |
||
112463 | Interface editor | The renaming of the in-/outputs in the interface editor might not update the dirty flag as expected.
Scenario for problem: If you rename an in-/output in the interface editor by using the command Edit Name or the F2-key, the name of the in-/output is changed in this editor but the dirty flag might not be displayed for the interface editor. Additional information: The problem has been detected for some workstations only. On other workstations, the problem did not occur (so the dirty flag has been displayed as expected). At present, there are no details on any differences between the workstations or for the deviations on the scenario performed on the workstations. Workaround: none existing |
||
112473 | FBD-editor | Unexpected message on a failed resizing of a block with a fixed size.
Scenario for problem: If the setting Fixed Size is checked within the interface editor, it is impossible to make a call of the block larger or smaller. When you try to enlarge such a call to adjust the size of several FBD-elements in one by using the commands Layout and Same Size, this unexpected message is displayed: A selected block cannot be made smaller because of a minimum height or width for the block. Workaround: none existing |
||
112484 | Application navigator | It is impossible to move a global-object into a namespace folder.
Scenario for problem: When you are using namespace folders in the application navigator, it is impossible to move a global-object from a regular folder into the namespace folder. Compare: It is possible to create a global-object in this namespace folder. Workaround: Removing the namespace assignment so that the folder becomes a regular folder. Move the global-object into this folder. Then turn the folder into a namespace folder again. |
||
112503 | Instances view | The context menu in the “Instances” view might not be displayed for the first mouse click.
Scenario for problem: A context menu is usually displayed in the “Instances” view if you click the →secondary mouse button (= press and release) in this view. But this is not true for the first time clicking this mouse button in the view. Workaround: Click the secondary mouse button a 2nd time to display the context menu. |
||
112508 | Application navigator, library configuration | The Application folder does not display the expected content for a library configuration.
Scenario for problem: When you create a library configuration in the Application folder, 2 items are displayed instead of the expected object for the library configuration:
Workaround: none existing |
||
112570 | Global-variables-editor | Duplicate global variables are possible in the global-variables-editor.
Scenario for problem: When you sort the existing global variables and then you change the section of the global variable that is the last item in the editor, the global-variables-editor displays a duplicate for the global variable just modified. Workaround: Save the changes in the editor, close and reopen the editor. Then the editor does not display the duplicate variable anymore. |
||
112666 | Team monitor view | The wrong timestamp is displayed for a locked object.
Scenario for problem: The column “Locked on” in the list under “Locked by me” of the team monitor displays a wrong timestamp for a locked object. Workaround: none existing |
||
112671 | Team monitor view | The context menu for the team monitor might not be opened at the current mouse position.
Scenario for problem: If you use a different screen scaling than 100%, the context menu for the team monitor is opened at a different position than the current mouse position. Workaround, if this is sensible: Use a screen scaling of 100%. Or use the keyboard shortcut, if such a shortcut is provided for the command provided in the context menu. |
||
112676 | FBD-editor | The opening of an FBD function block takes longer than expected.
Scenario for problem: The opening of a specific FBD function block takes up to 5 seconds. In previous versions, this opening of this block took only up to 1 second. Workaround: none existing |
||
112681 | FBD-editor | The command “Add Variable to Values of Variables” might create a duplicate of the view.
Scenario for problem: When you perform the following steps, a duplicate view of Values of Variables is displayed (instead of bringing the existing view to the front):
Workaround: none existing |
||
112826 | FBD-editor, smart styling |
A temporary size for a value field makes it impossible to position the value field onto the grid. As a consequence, the connection line to a block input is not a straight line.
Workaround: none existing |
||
112869 | Building the application, FORCEMRK block |
A
As a consequence, it is not possible to build the application. |
||
113596 | Application navigator, IDE |
The application navigator does not display the project name, when the project is closed/opened by using the gRPC interface.
|
||
113681 | Debugging the application |
Debugging is not possible. Reason: The call hierarchy in the Debug view is not automatically expanded and a hit breakpoint is not highlighted.
|
||
113759 | IDE |
It is not possible to use the gRPC interface for different instances of the IDE.
Also, the error log of the IDE displays errors that indicate exceptions. Here are some examples for these errors:
Additional information: By using the gRPC interface, it is possible to automate specific user actions in the IDE. |
||
113780 | FBD-editor |
When using at least 2 monitors with different screen scaling, the context menu for the FBD-editor is displayed in the wrong position.
|
||
113793 | Creating a custom library |
A specific library cannot be created by using “DEPLOY=:OBJECT” when “DEPLOY=:SOURCE” is working.
Additional information: The keyword |
||
113904 | Application navigator, Custom library |
When expanding a library, the application navigator might display the wrong content. Also, the expanding of the library takes longer than expected.
|
||
114008 | FBD-editor |
It is not possible to copy and paste a value field containing an ARRAY variable as expected.
|
||
114239 | Command line interfaces, custom libraries |
An insufficient warning might be displayed when using the tool for the automated generation and deployment of a library.
Additional information: At present, there are no details on the actual cause of the problem. |
||
114388 | IDE documentation |
Parts of the German IDE documentation for the current version are still provided in English.
|
||
114440 | PLCopen blocks, IDE documentation |
The IDE documentation for the PLCopen blocks contains wrong information about the values for the data type SAFEBOOL.
|
||
114497 | Application navigator, Project explorer |
A project folder that is renamed outside the IDE results in duplicated folders/files.
|
||
114525 | ST-editor, building the application |
The application cannot be built if an external variable is declared within a method and this method is declared within a class.
|
||
114558 | Device topology transformer (DTT) |
Missing VarCfg-objects in the project might cause an exception when the DTT has been used to generate these project elements.
Additional information:
Workaround: Use the device topology transformer (DTT) again to generate the project elements including the missing VarCfg-objects. |
||
114573 | PLC object, artifact identity, building the application |
An invalid artifact identity is caused when a program instance is disabled in the application navigator.
|
||
114589 | Command line interfaces, artifact identity, building the application |
The tool for the automated builds of applications does not consider invalid artifact identities as errors for the build.
|
If your problem is not listed in this list, check these sections: Troubleshooting and FAQ
Addendum: Known issues after the release of Neuron Power Engineer version 3.25.0
This section was last updated on: 2024-07-11
For issues discovered after the release of Neuron Power Engineer version 3.25.0, please refer to the release notes of the successor versions. Both the list of known problems and the list of fixed problems might contain descriptions of problems that are relevant for Neuron Power Engineer version 3.25.0.
Issues that have been reported before the successor version has been released are listed below. This list is updated at regular intervals (see the date after the section heading). If you need more up-to-date information, please contact Neuron .
ID |
Component |
Known problem |
---|---|---|
114612 | System libraries, Output messages |
The version number of the system library is missing in the German message about updating this system library.
|
114640 | IDE | Some customer versions might use outdated branding.
Scenario for problem: The branding of previous versions has been changed to include the product name "Neuron Power Engineer". However, some customer versions still use the outdated branding, for example the startup illustrations displays the previous product name. Workaround: none existing |
114651 | Safety parameter editor |
The keyboard shortcut Ctrl+Shift+S is not supported for the safety parameter editor.
|
114659 | “Values of Variables” view, Artifact identity |
An invalid artifact identity is caused when all variables are removed from the “Values of Variables” view.
|
114667 | “Instances” view, FBD-editor, smart styling |
Opening of the POU from the “Instances” view might take longer than expected. Scrolling in this POU also might take longer than expected.
|
114674 | Artifact identity |
Removing an object with an invalid artifact identity might not refresh the project content as expected.
|
114681 | Application navigator |
An exception is caused when a global variable is dropped onto a program instance.
|
114688 | Application navigator, Artifact identity |
An invalid artifact identity is caused when a namespace folder is renamed.
|
114695 | LD-editor, Debugging |
Double-click onto an OLT-field does not open the dialog to change the value.
|
114718 | FBD-editor |
After inserting several FBD-elements, an exception might be caused and the connection lines might not be displayed as expected.
Workaround: Save, close and reopen the FBD-editor. |
114732 | Teaming up to create applications |
Pasting resources might not lock the pasted resource.
|
114740 | Teaming up to create applications | Deleting resources might take longer than expected.
Scenario for problem: When you use a team server and delete some resources in a project, deleting 10 resources might take up to 40 seconds. Workaround: none existing |
114766 | Artifact identity, ST-editor |
Inaccurate validations of the artifact identity might be caused when an ST-object is deleted outside of the IDE but its ST-editor has been opened inside the IDE.
Additional information: When you check the artifact identity or you build the application, a dialog about the artifact identities reports the state of H-/C-files to be “Removed”. The additional description informs that the files have been removed. However, these files have not been deleted outside the IDE. |
114811 | Test framework |
PiL-tests are failing on a specific customer hardware platform.
|
Checksum for components of Neuron Power Engineer version 3.25.0
This section is not relevant for Neuron Power Engineer version 3.25.0.
Component |
Version |
Checksum |
Description |
---|---|---|---|
Neuron Power Engineer IDE |
version 3.25.0 |
|
|
system library |
version 3.8.0 |
|
|
system library |
Version 1.3.0 |
|
|